Process Enablement in Network Downtime Condition

ABSTRACT

It is a first aspect of the present disclosure to provide a computer implemented method of enabling a peripheral device connected to a network during an inactive communication with the network, that includes activating an ad-hoc network connection with a mobile device during the inactive communication of the peripheral device with the network; transmitting a document to the mobile device for processing; receiving the processed document from the mobile device; storing the processed document in a memory of the peripheral device; and sending the processed document to a remote storage location once the peripheral device is determined to be actively communicating with the network

CROSS REFERENCES TO RELATED APPLICATIONS

None.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

None.

REFERENCE TO SEQUENTIAL LISTING, ETC.

None.

BACKGROUND

1. Technical Field

The present disclosure relates generally to a method for enablingprocesses of a device and, more specifically, enabling processes of adevice during a network downtime condition.

2. Description of the Related Art

In many environments that rely on electronic and paper-based processes,there is a reliance on a network infrastructure to effectively andefficiently perform process-oriented work tasks. If the networkinfrastructure becomes unavailable (i.e., a network downtime conditionoccurs) through planned or unplanned network outages, the access tocritical process elements and steps may also become unavailable.Examples of network-based process elements or steps include, but are notlimited to, accessing centrally located documents and forms (such as ona server or in a remote storage location), processing workflow steps(such as scanning documents to an electronic file share) and completingfield entries in forms utilizing electronically stored data.

In many cases, once the network becomes unavailable, workers shift fromelectronic process entry to a more manual process, such as paper-basedprocessing. The manual processing of forms and documents may lead to ahigher potential for error and a less efficient processing of documents.Additional labor may also be needed once the network is back up orrunning in order to process the data that was manually captured on paperduring the network downtime condition.

Thus, there is a need for a solution that will enable a device tocontinue utilizing network-based processes during network downtime(i.e., where communication with a network is unavailable). There is alsoa need for a solution that will maintain efficient and accurateprocessing of documents with minimal procedural or process changes whena network infrastructure is unavailable.

SUMMARY

A system and methods of enabling a peripheral device connected to anetwork during an inactive communication with the network are disclosedherein. One example embodiment of enabling the device may includeactivating an ad-hoc network connection with a mobile device during theinactive communication of the peripheral device with the network,transmitting a document to the mobile device for processing, receivingthe processed document from the mobile device, storing the processeddocument in a memory of the peripheral device, and sending the processeddocument to a remote storage location once the peripheral device isdetermined to be actively communicating with the network.

In one aspect of the example embodiment, the peripheral device mayreceive a request for the document prior to the sending of the documentto the mobile device. In another aspect, the peripheral device mayautomatically perform the sending the processed document once theperipheral device is determined to be actively communicating with thenetwork.

In another aspect of the example embodiment, an updated copy of thedocument may be received from the remote storage server by theperipheral device. In another aspect, the processing may includecapturing barcode information. In yet another aspect of the exampleembodiment, storing the processed document may include adding theprocessed document to a queue of one or more documents stored in thememory. In another aspect, the method may further include sending theone or more documents to the remote storage location once the peripheraldevice is determined to be actively communicating with the network.

From the foregoing disclosure and the following detailed description ofvarious example embodiments, it will be apparent to those skilled in theart that the present disclosure provides a significant advance in theart of methods for enabling network-based processes in a device during anetwork downtime condition. Additional features and advantages ofvarious example embodiments will be better understood in view of thedetailed description provided below.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-mentioned and other features and advantages of the presentdisclosure, and the manner of attaining them, will become more apparentand will be better understood by reference to the following descriptionof example embodiments taken in conjunction with the accompanyingdrawings. Like reference numerals are used to indicate the same elementthroughout the specification.

FIG. 1 is one example embodiment of a networked system.

FIG. 2 is a flowchart of one example method for enabling a device of thesystem of FIG. 1 to perform network-based document processing during anetwork downtime condition.

DETAILED DESCRIPTION OF THE DRAWINGS

It is to be understood that the disclosure is not limited to the detailsof construction and the arrangement of components set forth in thefollowing description or illustrated in the drawings. The disclosure iscapable of other example embodiments and of being practiced or of beingcarried out in various ways. For example, other example embodiments mayincorporate structural, chronological, process, and other changes.Examples merely typify possible variations. Individual components andfunctions are optional unless explicitly required, and the sequence ofoperations may vary. Portions and features of some example embodimentsmay be included in or substituted for those of others.

The scope of the disclosure encompasses the appended claims and allavailable equivalents. The following description is, therefore, not tobe taken in a limited sense, and the scope of the present disclosure isdefined by the appended claims.

Also, it is to be understood that the phraseology and terminology usedherein is for the purpose of description and should not be regarded aslimiting. The use herein of “including,” “comprising,” or “having” andvariations thereof is meant to encompass the items listed thereafter andequivalents thereof as well as additional items. Further, the use of theterms “a” and “an” herein do not denote a limitation of quantity butrather denote the presence of at least one of the referenced item.

In addition, it should be understood that example embodiments of thedisclosure include both hardware and electronic components or modulesthat, for purposes of discussion, may be illustrated and described as ifthe majority of the components were implemented to solely in hardware.

It will be further understood that each block of the diagrams, andcombinations of blocks in the diagrams, respectively, may be implementedby computer program instructions. These computer program instructionsmay be loaded onto a general purpose computer, special purpose computer,or other programmable data processing apparatus to produce a machine,such that the instructions which execute on the computer or otherprogrammable data processing apparatus may create means for implementingthe functionality of each block or combinations of blocks in thediagrams discussed in detail in the description below.

These computer program instructions may also be stored in anon-transitory computer-readable medium that may direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablemedium may produce an article of manufacture, including an instructionmeans that implements the function specified in the block or blocks. Thecomputer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions that execute on the computer or other programmableapparatus implement the functions specified in the block or blocks.

Accordingly, blocks of the diagrams support combinations of means forperforming the specified functions, combinations of steps for performingthe specified functions and program instruction means for performing thespecified functions. It will also be understood that each block of thediagrams, and combinations of blocks in the diagrams, can be implementedby special purpose hardware-based computer systems that perform thespecified functions or steps, or combinations of special purposehardware and computer instructions.

Disclosed are a system and methods for enabling network-based processingby a computing device connected to a network during a period of aninactive communication with the network. According to one exampleembodiment of the present disclosure, when the computing device isdetected to be inactively connected to the network such as, for example,during a network downtime, the computing device may activate an ad-hocnetwork connection with a mobile device. The computing device may thensend the document to be processed to the mobile device. In one exampleembodiment, the mobile device may perform the network-based process onthe document such as, for example, inputting or completing informationon the document. Upon completion of the network-based processing of thedocument by the mobile device, the processed document may be sent to thecomputing device for further processing and/or storing into a queueuntil the computing device is determined to be in an activecommunication with the network.

The system and methods described herein may enable workflow solutions tocontinue with minimal procedural or process changes when the networkinfrastructure is unavailable either through a planned or unplannednetwork outage or when the computing device loses its communication withthe network. The example embodiments described herein may be achieved byutilizing storage and ad-hoc networking capabilities along with formsserver logic on a computing device or appliance.

FIG. 1 is one example embodiment of a networked system 100, according toone example embodiment of the present disclosure. System 100 is a datacommunication system that may include a client device 105, a remotecomputer 110 and a multi-function printing device (MFP) 115. Remotecomputer 110 and MFP 115 may be connected through a network 120.

Client device 105 may be any computing device. In one exampleembodiment, client device 105 may be, for example, a personal computer.Client device 105 may include a display unit, an input device (e.g.,keyboard), a processor, and memory, such as RAM, ROM, and/or NVRAM.Client device 105 may also include a mass data storage device, such as ahard drive, CD-ROM and/or DVD units. During operation, client device 105may include in its memory a software program including programinstructions that function as a document processing application forprocessing one or more documents received from MFP 115. Client device105 may include an imaging driver (not shown) that may communicate withMFP 115 via a communications link. In addition, the imaging driver mayprovide processed documents for storing and/or printing by MFP 115.

In another example embodiment, client device 105 may be any computingdevice that is portable, handheld or pocket-sized such as, for example,a mobile device (e.g., a cell phone), a smart phone, a handheldcomputer, a personal digital assistant (PDA), a notebook computer, atablet computer, or any other remote computing device, such as aspecial-purpose remote computing device (e.g., e-book reader).Additionally, client device 105 may include at least one control unitsuch as, for example, a processor (not shown) that controls theoperation of the computing device.

MFP 115 may be network-enabled and capable of communicating with remotecomputer 110. For example, MFP 115 may be connected to remote computer110 via a communication link, which may be established by a wired orwireless connection such as, for example, an Ethernet connection. MFP115 may be any device capable of printing or producing a hard copy datafile or document stored in electronic form, such as a laser, inkjet ordot matrix printer or a multi-function printing device capable ofperforming other functions, such a faxing, e-mailing, scanning and/orcopying, in addition to printing.

MFP 115 may include a control unit and a print engine. The control unitof MFP 115 may include one or more embedded solutions that may store andprovide templates or copies of one or more documents for use by a userof MFP 115. In some example embodiments, the embedded solution may be asoftware application that may be stored in a non-transitory computerreadable storage medium associated with the control unit and may beexecuted by the control unit in accordance with programmed logicassociated with the software application.

In one aspect, MFP 115 may include a processor (not shown) incommunication with a user interface (not shown), a memory (not shown),and a scanning subsystem (not shown). The user interface may be agraphical user interface, a monitor, a series of buttons, atouch-sensitive display panel, a text interface such as a 2-linedisplay, and a voice-activated interface or the like. In one aspect, theuser interface may serve as an operating panel for MFP 115. It is alsowithin the scope of this aspect to utilize a computer (not shown), suchas personal computer, having a monitor as the user interface. Thoseskilled in the art will appreciate that MFP 115 may include variousadditional components, such as a facsimile, scanner and/or card reader.MFP 115 may also include one or more appropriate software applicationsconfigured to receive print data or one or more files from a printserver (not shown) and to output or print pages through a print engine(not shown) of MFP 115.

MFP 115 may be connected to network 120 by a direct cable or opticalconnection or by a network connection such as, for example, an Ethernetlocal area network (LAN). The connection between MFP 115 and network 120may be established by an Internet connection, or via a wide area network(WAN). Communication links between MFP 115 and network 120 may beestablished by using standard electrical cabling or bus structures. Thecommunication links may also be established using wireless connections.Where the communication links are wireless, MFP 115 may further includea radio transceiver. The wireless connection may be, for example, 2G,3G, Bluetooth, CDMA, DECT, TDMA, UMTS-TDD, WiBro, WiFi, or WiMAX. Wiredconnections may be proprietary or constructed in accordance with ancommunications industry standard, such as USB or FireWire (IEEE-1394).

When used in a LAN networking environment, MFP 115 may be connected tothe local area network through a network interface or adapter. When usedin a WAN networking environment, MFP 115 may include a modem, T1 line,satellite or other means for establishing communications over a widearea network, such as the Internet. The modem, which may be internal orexternal, may be connected to a system bus of MFP 115 via a serial portinterface.

In a networked environment, program modules, applications or workflowsolutions, or portions thereof, performed by MFP 115 may be stored inlocal or remote memory storage devices. In some example embodiments, MFP115 may be linked to other processing devices in order to performcertain tasks. It will be appreciated that the network connectionsdescribed are illustrative and other means of establishing acommunications link between the computing devices may be used.

MFP 115 may store in its memory one or more electronic documents thatmay serve as local copies of forms or templates which a user of MFP 115may use for data input and/or processing. For example, in the healthcareindustry, the forms or templates may include, but are not limited to,patient intake forms, patient records, medical history forms, reportingand billing forms, and other types of documents. The local copies of theforms or templates may be stored in the memory of MFP 115, such thatwhen a user of MFP 115 wishes to print a copy of the form to be filledin with information, the user may simply operate the MFP 115 to retrievea copy of the form or template from its memory and print a hard copy.Having local copies of the electronic forms allows the form templates tobe readily available for use as desired or needed, thus eliminating theneed for MFP 115 to connect to a remote storage server every time a userof MFP 115 wishes to use a copy of the one or more form templatesavailable in the memory of MFP 115.

During use, MFP 115 may operate in a networked environment using logicalconnections to one or more other computing configurations, such asremote computer 110. Remote computer 110 may be a personal computer, aserver, a router, a network PC, a peer device or other common networknode. As set forth above, the logical connections between MFP 115 andremote computer 110 may include a local area network (LAN) and/or a widearea network (WAN).

In one example embodiment, remote computer 110 may be a central captureor repository service that may be used to store electronic documentscontaining information gathered using MFP 115. For example, remotecomputer 110 may be a centralized document management system such as,for example, a Health Information Management System (HIMS).

In one example embodiment, remote computer 110 may provide updatedversions of the local copies of the electronic form documents ortemplates stored in MFP 115. For example, when the local copies of theform templates are updated with a new version, remote computer 110 mayprovide MFP 115 with the newer versions of the form templates through anupdate.

Updating the local copies of the form templates in MFP 115 may includeautomatically delivering updated copies to MFP 115. Automatic deliveryof updated copies may be performed by either a pull method or a pushmethod. In the pull method, MFP 115 may periodically poll the remotecomputer 110 to ensure it has the most recent versions of the forms inits memory. In another example embodiment, a central forms server maystore the form templates, and MFP 115 may periodically poll the centralforms server for updated copies of form templates.

In the push method, MFP 115 may use subscription services such as, forexample, Really Simple Syndication (RSS), in order to be notified whenupdates are available and/or when an action is required to update thelocal copies of the form templates. A means to register MFP 115 forsyndication services may be utilized to ensure correct and current formsare available on MFP 115. Syndication services for subscribing toupdates as described herein is illustrative and should not be consideredlimiting. Other subscription services as will be known in the art may beused in some alternative example embodiments.

Client device 105 and MFP 115 may connect and communicate wirelesslythrough short-range, ad hoc networks, which may be establisheddynamically and automatically as the client device 105 and MFP 115 enterand leave radio proximity to each other.

With continued reference to FIG. 1, network 120 may be any network,communications network, or network/communications network system suchas, but not limited to, a peer-to-peer network, a hybrid peer-to-peernetwork, a Local Area Network (LAN), a Wide Area Network (WAN), a publicnetwork, such as the Internet, a private network, a cellular network, acombination of different network types, or other wireless, wired, and/ora wireless and wired combination network capable of allowingcommunication between two or more computing systems, as discussedherein. Other types of networks and communications mode may be used toconnect client device 105, MFP 115 and remote computer 110 from eachother, as will be known in the art.

Although the system in FIG. 1 shows only one client device 105, one MFP115 and one remote computer 110, networked system 100 may have anynumber of components and devices, as will be appreciated by one ofordinary skill in the art.

FIG. 2 is a flowchart of one example method 200 for enabling a device,such as MFP 115 of networked system 100, to perform network-baseddocument processing during a network downtime condition orcommunications loss between the device and remote computer 110. Method200 may enable workflow solutions to continue with minimal procedural orprocess changes during such outages.

Method 200 may include determining if the device is actively connectedto network 120, activating an ad-hoc network connection with a clientdevice, sending a document to the client device, processing thedocument, and storing the document in a memory of the device fortransmission to a remote computer when network 120 is determined to bein an uptime condition or communication is re-established between thedevice and network 120. Allowing ad-hoc network connections to beestablished between the device and a client device enables electronictransfer of a downtime document for processing by client device 105.This transfer enables electronic capture of data into the document for ahigher efficiency and success rate of processing information.Availability of the electronic downtime form may also minimize thechanges in process and procedure regardless of network state.

With reference to FIG. 2, at block 205, it is determined whether MFP 115is actively connected or communicating with network 120. An activeconnection with network 120 may refer to a state wherein MFP 115 is ableto communicate with a node in network 120 that is connected to MFP 115such as, for example, remote computer 110.

In one example aspect, determining if MFP 115 is in active connection orcommunication with network 120 may include determining whether network120 is in an uptime or downtime condition. A network uptime conditionmay refer to a period during which network 120 is operational, and MFP115 is able to communicate with other nodes in network 120. A networkdowntime condition may refer to a period during which network 120 isdetermined to not be operational, and communication with other nodes innetwork 120 is unavailable. A network downtime condition may occurduring planned outages such as, for example, during routine maintenance.Network downtime condition may also occur during unplanned outagescaused by unexpected factors such as, for example, communication andsystem failures. Other factors that may cause network downtime conditionwill be apparent to one of ordinary skill in the art.

In another example aspect, determining if MFP 115 is in activeconnection or communication with network 120 may include determiningwhether MFP 115 is able to connect or communicate with the device neededto perform the network-based processing. For example, if the formtemplates are stored on remote computer 110, and the network-basedprocessing is the downloading of updated forms to MFP 115, MFP 115 is inactive communication with network 120 if MFP 115 is able to communicatewith remote computer 110 and receive the updated forms.

A means to detect a network downtime condition may be incorporated inMFP 115 such as, for example, an attempt to contact remote computer 110.The attempt to contact remote computer 110 may return a positive ornegative feedback. In some example embodiments, positive feedback mayindicate a successful communication link between MFP 115 and remotecomputer 110 and vice-versa while negative feedback may indicate anunsuccessful or failed communication between MFP 115 and remote computer110. Signals indicating a positive or a negative feedback may beprovided by MFP 115 accordingly.

At block 210, if MFP 115 is determined to be in an inactive connectionto network 120 indicating a network downtime condition or failure tocommunicate with remote computer 110, a means for establishing ad-hocnetwork connection may be activated in MFP 115 to connect MFP 115 toanother device such as, for example, client device 105. Ad-hoc networkconnection may refer to a feature of the IEEE 802.11 standard. The adhoc communications mode allows the radio network interface card (NIC) ofMFP 115 to operate in what the IEEE 802.11 standard refers to as anindependent basic service set (IBSS) network configuration. In an IBSSconfiguration, devices may communicate directly with each other withoutan intermediary, e.g., without an access point device.

MFP 115 may include a wireless radio to allow for proximity ad-hocconnections. In some example embodiments, other means for establishing aconnection between MFP 115 and client device 105 may be performed byusing proximity-based protocols such as, for example, wireless USB andNFC. In yet other example embodiments, other means for connecting MFP115 to client device 105 may be used, as will be known in the art.

At block 215, after MFP 115 and client device 105 have successfullyestablished a connection or communications link, client device 105 mayquery MFP 115 for a document stored in MFP 115. For example, clientdevice 105 may query MFP 115 for a template or a blank form that may befilled in or completed with information or data using client device 105.Example information for a healthcare template or form may include, forexample, a patient's personal data (e.g., name, address, marital status,etc.), the date, the time, diagnosis, etc. It will be appreciated bythose skilled in the art that other information or data may be used tocomplete templates or forms used in other industries.

At block 220, MFP 115 may send the document or template queried byclient device 105 to client device 105. Sending the document may includesending the queried document from MFP 115 to client device 105 throughthe ad hoc network connection established at block 210. In some exampleembodiments, other means for sending the document from MFP 115 to clientdevice 105 may be used, as is known in the art.

At block 225, the document or template may be processed by client device105. In one example embodiment, processing the document may includepopulating the form with relevant information received from a user. Forexample, the user of client device 105 may process a form received fromMFP 115 by populating or inputting data into the fields in the form withinformation that is relevant to the form such as, for example, apatient's personal information.

In another example embodiment, processing the document may includecapturing a barcode and retrieving information from the barcode topopulate the document. Capturing the barcode may include taking an imageof the barcode using a camera, a barcode scanner or any image-capturingand/or information-retrieving component included in client device 105.For example, in a healthcare scenario, a healthcare worker may downloada form from MFP 115 to client device 115; select a specific process orworkflow by launching an information-retrieving application, such as abarcode scanning application; and capture a patient's barcode (e.g.,from a wristband or a chart). An application in client device 115 mayautomatically fill in or complete the proper fields on the form usingthe retrieved information from the barcode. When information isretrieved from a barcode, the need for manual user input may beeliminated, or at least reduced.

Upon retrieving information from the barcode, fields in the document maybe automatically completed or filled in with the retrieved information.Filling in the fields in the document may include utilizing forms logicto fill in the correct fields with the retrieved barcode information(e.g., filling in the patient name in the field corresponding to thepatient name, filling in the patient number in the field correspondingto the patient number, etc.). In some example aspects, filling in thefields may also involve process steps such as, for example, recording ameasurement such as patient temperature and/or marking the process ascompleted along with recording a timestamp. In other example aspects,steps may also include filling in contextual information such as time,date, location, and/or identification of the clinician performing theprocess steps, etc.

At block 230, client device 105 may send or transmit the processeddocument to MFP 115, and MFP 115 may store the processed document in itsmemory. In one aspect, storing the processed document may include addingthe document to a queue of one or more processed documents to beautomatically sent to remote computer 110 for storage once MFP 115 isdetermined to be in active communication with network 120 and remotecomputer 110. For example, the electronic form completed in clientdevice 105 may be sent to MFP 115 for submission into remote computer110. In another aspect, MFP 115 may check for an uptime condition ofnetwork 120 and/or active connection with remote computer 110 whilestoring the processed document in its memory, and when MFP 115 isdetermined to be in active connection with remote computer 110, MFP 115may submit the completed electronic form to remote computer 110 forstorage.

In another aspect, storing the processed document may include adding thedocument to a queue of one or more processed documents to be sent to acentralized document management system or central storage repository forstorage once MFP 115 is determined to be in active communication withnetwork 120. For example, the electronic form completed in client device105 may be sent to MFP 115 for submission into the centralized documentmanagement system for storage once communication with network 120 isre-established.

In some example alternative embodiments, MFP 115 may store the processeddocument in its memory until an active communication with network 120 isdetected, and the remote computer 110 or central storage repositoryrequests transmission of the processed documents for storing.

It will be understood that the example applications described herein areillustrative and should not be considered limiting. It will beappreciated that the actions described and shown in the exampleflowcharts may be carried out or performed in any suitable order. Itwill also be appreciated that not all of the actions described in FIG. 1need to be performed in accordance with the embodiments of thedisclosure and/or additional actions may be performed in accordance withother embodiments of the disclosure.

Many modifications and other example embodiments of the disclosure setforth herein will come to mind to one skilled in the art to which thesedisclosure pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the disclosure is not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

What is claimed is:
 1. A method of enabling a peripheral deviceconnected to a network, comprising: activating an ad-hoc networkconnection with a mobile device during an inactive communication of theperipheral device with the network; transmitting a document to themobile device for processing; receiving the processed document from themobile device; storing the processed document in a memory of theperipheral device; and sending the processed document to a remotestorage location once the peripheral device is determined to be activelycommunicating with the network.
 2. The method of claim 1, wherein theperipheral device receives a request for the processed document prior tothe sending.
 3. The method of claim 1, wherein the peripheral deviceautomatically performs the sending the processed document to the remotestorage location once the peripheral device is determined to be activelycommunicating with the network.
 4. The method of claim 1, furthercomprising receiving an updated copy of the document from the remotestorage server.
 5. The method of claim 1, wherein the processingincludes capturing barcode information.
 6. The method of claim 1,wherein the storing the processed document includes adding the processeddocument to a queue of one or more documents stored in the memory. 7.The method of claim 6, further comprising sending the one or moredocuments in the queue to the remote storage server once the peripheraldevice is determined to be actively communicating with the network.
 8. Acomputing device with a non-transitory computer-readable storage mediumcontaining computer executable instructions to: initiate an ad-hocnetwork connection with a client device if the computing device is notactively connected to a network; send a document to the client devicefor processing; receive the processed document from the client device;store the processed document in a memory of the computing device, untilthe computing device is determined to be actively connected to thenetwork; and send the stored processed document to a remote storagelocation once the computing device is determined to be activelyconnected to the network.
 9. The computing device of claim 8, whereinthe initiating the ad-hoc network connection includes connecting to theclient device using a wireless radio in the computing device.
 10. Thecomputing device of claim 8, wherein the initiating the ad-hoc networkconnection includes connecting to the client device using one or moreproximity-based protocols.
 11. The computing device of claim 8, furthercomprising a computer executable instruction to receive an updated copyof the document from the remote storage location.
 12. The computingdevice of claim 8, further comprising a computer executable instructionto periodically poll the remote storage location for an updated copy ofthe document.
 13. A method of enabling form processing of a deviceconnected to a network during downtime of the network, comprising:automatically determining if the network has returned to operation; ifthe network has not returned to the operation, activating an ad-hocnetwork connection with a mobile device; sending a form to the mobiledevice for population of fields; receiving the populated form from themobile device; storing the populated form in a memory of the deviceuntil the network is determined to have returned to the operation; andsending the stored populated form to a remote storage location once thenetwork is determined to have returned to the operation.
 14. The methodof claim 13, further comprising storing a copy of the form in the memoryof the device.
 15. The method of claim 13, further comprising receivingan updated master form from the remote storage location.
 16. The methodof claim 13, further comprising periodically polling a remote storageserver to check for an updated form.
 17. The method of claim 13, whereinthe storing the populated form includes adding the populated form to aqueue of one or more populated forms stored in the memory.
 18. Themethod of claim 17, further comprising automatically sending the one ormore populated forms in the queue to the remote storage location oncethe network is determined to return to the operation.
 19. The method ofclaim 17, wherein the activating the ad-hoc network connection includesconnecting to the mobile device using a wireless radio.
 20. The methodof claim 17, wherein the activating the ad-hoc network connectionincludes connecting to the mobile device using a proximity-basedprotocol.